Mark tsconfig files as JSONC for linguist#3573
Conversation
This will help GitHub's syntax highlighting to correctly display comments in tsconfig files.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Marks tsconfig*.json files as JSON-with-Comments for GitHub Linguist so GitHub renders comments correctly (no “invalid JSON” highlighting) in tsconfig files.
Changes:
- Add a
.gitattributesrule to classifytsconfig*.jsonasJSON-with-Commentsfor Linguist.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates Git attributes so GitHub Linguist treats tsconfig files as JSON-with-comments, improving syntax highlighting for commented tsconfig*.json files.
Changes:
- Add Linguist language overrides for
tsconfig.jsonandtsconfig.*.jsonvia.gitattributes.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| tsconfig.json linguist-language=JSON-with-Comments | ||
| tsconfig.*.json linguist-language=JSON-with-Comments |
There was a problem hiding this comment.
I think the language name is already correct with the -.
This will help GitHub's syntax highlighting to correctly display
comments in tsconfig files.
For example, note the "invalid" (red) syntax highlighting here:
wordpress-playground/packages/playground/client/tsconfig.lib.json
Lines 14 to 20 in ecff239